home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970929-19971216
/
000341_news@newsmaster….columbia.edu _Sat Dec 6 05:49:05 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id FAA06422
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 6 Dec 1997 05:49:04 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id FAA14707
for kermit.misc@watsun; Sat, 6 Dec 1997 05:49:04 -0500 (EST)
Path: news.columbia.edu!news.new-york.net!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!newsfeed.internetmci.com!128.158.254.10!news.msfc.nasa.gov!info.usuhs.mil!news.monroe.army.mil!wrdiss1.robins.af.mil!wpdiss1.wpafb.af.mil!oodiss1.hill.af.mil!news.cc.utah.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Why suddenly "Too many macro names"???
Message-ID: <WiFh3$Bqwotb@cc.usu.edu>
Date: 5 Dec 97 08:33:45 MDT
References: <19971205080201.DAA29956@ladder02.news.aol.com>
Organization: Utah State University
Lines: 18
Xref: news.columbia.edu comp.protocols.kermit.misc:8136
In article <19971205080201.DAA29956@ladder02.news.aol.com>, trock@aol.com (TRock) writes:
> I've just upgraded my application from using MS Kermit 3.12 to 3.15. After
> resolving some minor syntax changes andfiguring out where KERMIT was stashing
> it's 'connect' screens, it runs fine... for awhile, then suddenly I get a rash
> of messages "Too many macro names".... repeated until it hangs.
>
> Too many where? why? why only after several screen changes?
>
> Anyone got any enlightenment here?
---------
Nope, unless you can supply a few more details. What script was run,
some indication of how, and roughly where the "too many" msgs start appearing.
There are substantial changes to the script language between versions 3.12
and 3.15 of MS-DOS Kermit, and that's probably what trips up things. So it
would be a good idea to use the v3.15 scripts where possible.
To debug some, try SET TAKE ECHO ON to view script commands as they
are encountered. Look for endless loops.
Joe D.